Proposed changes

Allows authorized users to reset the encryption key of E2EE rooms.

The idea is to prevent situations where all users of a room have lost the keys, and with that, have lost the access to use the room. Now Rocket.Chat will allow them to define a new set of keys for the room via UI.

If a user happens to have a key to the room, after the reset this will be moved to a list of oldRoomKeys, which the UI will use to decode older messages.

Issue(s)

Implements RocketChat/Rocket.Chat#33328

How to test or reproduce

• User A (owner) and User B on the same E2EE room
  • Suggestion: do it with both users on mobile app on different simulators. This way you'll be able to follow along testing all features involved
• Send a few messages with both users
• User B is offline
• User A resets its own E2EE key on Settings > Security and privacy > E2EE > Reset
• User A logs in and app creates a new E2EE key automatically
• User A can't read the room, since they don't have keys
• User A resets room key
  • Can be done by tapping key icon on header or Room Actions > E2EE > Reset
• User A won't be able to read the messages still
• User A sends a few messages with the new key
• User A goes offline
• User B logs in again, receives the new key and provides old room keys to User A
• User B can read the messages User A just sent with the new key and all the old ones, since they had the keys all this time
• User A goes online and can read all messages again

Screenshots

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• Improvement (non-breaking change which improves a current function)
• New feature (non-breaking change which adds functionality)
• Documentation update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if applicable)
• I have added necessary documentation (if applicable)
• Any dependent changes have been merged and published in downstream modules

Further comments

CORE-802